发布 TraceFetch 1.0.1 安全修复 - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Why
PR #2 merged user-visible crawl receipt security and failure-contract fixes after v1.0.0. The existing GitHub Release still points to v1.0.0, so installation users cannot consume the accepted fix through an immutable release asset.
Impact and risk
This PR changes only release metadata, documentation, and release-contract tests. Product behavior is unchanged from current main. The release workflow will still rerun full gates, verify the tag, build wheel/sdist, smoke-install the wheel, and publish immutable GitHub Release assets. PyPI is not claimed.
Checks
make check: 135 passed, coverage 83.04%, Ruff, mypy, schemas, version check, wheel and sdist passedpython scripts/check_version.py --tag v1.0.1: passedtracefetch 1.0.1; local search schema smoke passedgit diff --check: passedproceed-to-closewith no P0/P1/P2 findingsRejected candidate findings
The first frozen diff left
docs/releasing.mdpinned tov1.0.0and used a weak README substring assertion. Both were corrected before commit; the final test requires exactly threev1.0.1README references, forbids stalev1.0.0, and verifies the version-agnostic release command.Evidence boundary
These checks prove source/version coherence, local buildability, an isolated wheel smoke, and review of the exact committed diff. They do not prove the PR is merged, the tag exists, the release workflow succeeds, GitHub assets are published, PyPI availability, production deployment, or user adoption.
Note
Low Risk
Only version strings, changelog, README, release docs, lockfile, and release-contract tests change; product behavior is unchanged from current main.
Overview
Release-only bump to 1.0.1 so immutable GitHub install paths and package metadata match the crawl receipt verification hardening already on
main.Version strings move to 1.0.1 in
pyproject.toml,tracefetch.__version__, anduv.lock. README install examples now referencev1.0.1(three places). CHANGELOG adds a 1.0.1 section documenting receipt verification, bounded failure output, and safer receipt file reads—not new code in this PR.Release docs replace a pinned
v1.0.0version-check example withvMAJOR.MINOR.PATCH. Release contract tests assertv1.0.1coherence, exactly three READMEv1.0.1references, no stalev1.0.0in README, and the generic release-doc command.Reviewed by Cursor Bugbot for commit eaa96aa. Bugbot is set up for automated code reviews on this repo. Configure here.